Node / meshtastic / Meshtastic-Android / files / docs / zh-rTW / user / telemetry-and-sensors.md

Displaying Rendered • View raw • Download

title: Telemetry & Sensors

parent: User Guide

nav_order: 9

last_updated: 2026-05-13

description: Sensor data on the mesh — supported environment, air quality, and power sensors, plus configuration and viewing guides.

aliases:

• sensors

• environment

• weather

• power-metrics

Meshtastic nodes can collect and share sensor data across the mesh network.

Telemetry allows nodes equipped with sensors to broadcast environmental, power, and device health information. This data is visible on the node detail screen and can be logged over time.

All Meshtastic nodes report basic device telemetry:

Supported environmental sensors:

Nodes with INA-series power sensors can report:

Useful for monitoring solar charging or battery health on remote nodes.

1. Navigate to Settings → Module Config → Telemetry.

2. Set reporting intervals:

• Device Metrics Interval — how often to broadcast device metrics

• Environment Metrics Interval — how often to broadcast sensor data

3. Enable specific sensor types as needed.

│ ⚠️ Note: Shorter intervals increase airtime usage and battery drain across the mesh.

Nodes with particulate matter or CO₂ sensors report air quality data:

CO₂ sensors such as the SCD4x also report their own temperature and humidity, which appear alongside the readings above. From PM2.5 history the app additionally derives an EPA NowCast AQI value.

The CO₂ reading is color-coded by severity (Good → Stuffy → Poor → Unsafe → Evacuate). See Node Metrics — Air Quality for the exact ppm bands, colors, and AQI detail.

Air quality data can be viewed as info cards on the node detail screen, charted over time, and exported to CSV.

1. Navigate to Nodes and select a node.

2. Telemetry sections show on the detail screen:

• Device Metrics (always available)

• Environment Metrics (if sensors present)

• Power Metrics (if INA sensor present)

• Air Quality Metrics (if PM/CO₂ sensor present)

3. Historical graphs show trends over time.

!Telemetry actions

• No environment data showing? The remote node needs a physical sensor connected (e.g., BME280 on I2C). Device telemetry (battery, uptime) is always available, but environment metrics require hardware.

• Stale readings? Check the reporting interval — very long intervals (7200s+) mean data updates infrequently. Also verify the remote node is still online.

• Sensor conflict on I2C bus? Some sensors share I2C addresses. If you have multiple sensors on the same bus, check for address collisions in the radio's serial debug output.

• Node Metrics — view telemetry data on the node detail screen

• Settings — Modules & Admin — telemetry module configuration

• Units & Locale — temperature and pressure display units